Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1526

reference: 239-tree-1
name: 1526
tree-preservation-order: undefined
239-tpo-1
uprn
address-text
point: POINT (-1.005383 50.854483)
geometry: MULTIPOLYGON (((-1.005298 50.854474,-1.005302 50.854490,-1.005314 50.854505,-1.005332 50.854518,-1.005356 50.854525,-1.005382 50.854528,-1.005409 50.854526,-1.005433 50.854518,-1.005452 50.854507,-1.005464 50.854492,-1.005469 50.854475,-1.005465 50.854458,-1.005453 50.854443,-1.005434 50.854431,-1.005411 50.854423,-1.005384 50.854420,-1.005358 50.854423,-1.005334 50.854430,-1.005315 50.854442,-1.005303 50.854457,-1.005298 50.854474)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL